5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
- Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 2-3: Domains

Common Domain Specifications


When you select Enter from the Domains screen title bar, the Domains specifications overlay displays. The following two entries, Descriptive and Column Hdgs, are common to the specifications overlay for all types of domains other than Same As domains:

Descriptive, if entered, establishes the Descriptive for all fields referencing the domain. However, since domain attributes cannot be overridden, you may wish to leave Descriptive blank here to allow for individual entry at the field level. Because Descriptive is longer and can be more flexibly formatted, itis less cryptic and easier to understand than Field Name. The system uses Descriptive when communicating with users wherever possible. It is used, for example, when the value of a field displays to a user on a standard image, such as the Select Access Path display or an APPX-generated subheading.

Column Hdgs, if entered,establishes up to two lines of column heading text for all fields referencing this domain. However, since domain attributes cannot be overridden, you may wish to leave Column Hdgs blank here to allow for individual entry at the field level. For cosmetic reasons, the length of a heading should not exceed the length of the field itself. The APPX output process uses column heading text to generate standard column heading images for Start of Page and Start of Range class frames.Refer to Output Process Specifications, Output Standard Column Heading Image, and Output Frame Specifications for more information on automatically generated column headings and frame classes in output functions.

Application Design Manual                                         "Powered by Appx Software"

151

©2006 By APPX Software, Inc. All Rights Reserved